Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@scripts/codex/check-codex-global-state.sh`:
- Line 116: The check embeds $section directly into the regex "^\[$section\]"
which treats dots and other metacharacters as wildcards; update the code that
calls search_file so it first escapes regex metacharacters in $section (e.g.,
via a small helper like escape_regex that backsslashes []\.^$*+?(){}| and so on,
or by using a literal/ fixed-string search if search_file supports it), then use
the escaped value when building the pattern (replace "^\[$section\]" with
"^\[$escaped_section\]"), referencing the search_file call, the $section
variable, and CONFIG_FILE in your change.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@skills/remotion-video-creation/rules/charts.md`:
- Line 14: Update the documentation text to correct the two typos: change the
phrase "third party" in the sentence "Disable all animations by third party
libraries." to the compound adjective "third-party", and correct the misspelling
"implmentation" to "implementation" wherever it appears (notably the instance on
line 20) in the charts.md content.
- Line 20: Update the broken link in charts.md that points to
"assets/charts/bar-chart.tsx": change the path to the correct asset file name
"assets/charts-bar-chart.tsx" (remove the non-existent "charts/" subdirectory
and use the hyphenated filename) so the Bar Chart Example link resolves to the
existing asset.

In `@skills/remotion-video-creation/rules/display-captions.md`:
- Around line 8-126: Reorganize the document to match the required "When to
Use", "How It Works", and "Examples" sections: add a brief "When to Use" that
describes scenarios for caption display, move the "Prerequisites" and the
createTikTokStyleCaptions usage (including useMemo and SWITCH_CAPTIONS_EVERY_MS)
plus the Sequence rendering logic (pages, Sequence,
startFrame/endFrame/durationInFrames) into a combined "How It Works" section,
and place the word-highlighting example (CaptionPage, useCurrentFrame,
useVideoConfig, TikTokPage, page.tokens and token timing logic) into an
"Examples" section; preserve all technical details and referenced symbols
(createTikTokStyleCaptions, pages, SWITCH_CAPTIONS_EVERY_MS, Sequence,
CaptionPage, TikTokPage) and ensure headings are Markdown-formatted as required.
- Around line 109-121: The current React key uses token.fromMs which can
collide; update the map callback in page.tokens.map to accept the index
(map((token, idx) => ...)) and set a stable unique key combining fromMs with
either the index or token text (e.g., `${token.fromMs}-${idx}` or
`${token.fromMs}-${token.text}`) on the <span> so keys are deterministic and
unique (change reference to token.fromMs in the key prop).

In `@skills/remotion-video-creation/rules/extract-frames.md`:
- Around line 196-205: The timeout Promise can still reject after
extractFrames() wins the race; change the Promise.race usage so the timeout
timer is cleared when extractFrames resolves: capture the timeoutId created
inside timeoutPromise (or move timeoutId to an outer scope), then when invoking
Promise.race([extractFrames(), timeoutPromise]) attach a .then/.finally handler
on the successful extractFrames call (or wrap extractFrames in a small wrapper)
to call clearTimeout(timeoutId) and remove any listeners on controller.signal;
reference timeoutPromise, timeoutId, controller.signal, extractFrames(), and the
Promise.race call to locate where to add the clearTimeout on success.
- Around line 8-191: The document is missing the required skill-document
sections; add explicit "When to Use", "How It Works", and "Examples" headings to
the markdown around the existing content so it matches the skills/*.md
format—insert a "When to Use" section summarizing scenarios for extractFrames(),
a "How It Works" section describing the flow (Input,
computeDuration/getFormat/getPrimaryVideoTrack, timestamps resolution,
VideoSampleSink.samplesAtTimestamps, AbortSignal handling) and an "Examples"
section that includes the provided usage, filmstrip, and cancellation snippets
(referencing ExtractFramesProps, extractFrames, and VideoSampleSink) so the doc
validates against the required structure.

In `@skills/remotion-video-creation/rules/fonts.md`:
- Line 36: Fix the spelling in the Markdown sentence "Preferrably, specify only
needed weights and subsets to reduce file size:" by replacing "Preferrably" with
"Preferably" wherever that exact phrase appears (e.g., in the fonts.md content
string) so the user-facing docs read "Preferably, specify only needed weights
and subsets to reduce file size:".
- Around line 8-152: Add the three mandatory skill doc sections "When to Use",
"How It Works", and "Examples" to this markdown: create a "When to Use" section
under the top-level "Using fonts in Remotion" that explains scenarios for
choosing Google vs local fonts, a "How It Works" section that briefly describes
the APIs and flow (mention `@remotion/google-fonts` loadFont and waitUntilDone,
and `@remotion/fonts` loadFont with staticFile), and an "Examples" section that
includes short, focused examples already in the file (the Google Fonts snippets
using loadFont from `@remotion/google-fonts` and the local font snippets using
`@remotion/fonts` + staticFile) so the doc conforms to the skills/**/*.md required
structure.

In `@skills/remotion-video-creation/rules/tailwind.md`:
- Around line 7-11: The skill doc is missing the required sections; add clear
Markdown headings "When to Use", "How It Works", and "Examples" to
skills/remotion-video-creation/rules/tailwind.md; under "When to Use" state when
Tailwind in Remotion is appropriate, under "How It Works" describe that Tailwind
must be installed/enabled (fetch https://www.remotion.dev/docs/tailwind using
WebFetch) and explain the rule "Don't use transition-* or animate-*; always
animate using useCurrentFrame()", and under "Examples" show one or two concise
examples demonstrating Tailwind utility classes for styling combined with an
animation implemented via the useCurrentFrame() hook (reference useCurrentFrame
and Tailwind classes in the text).

---

Nitpick comments:
In `@skills/lead-intelligence/agents/outreach-drafter.md`:
- Line 16: Add an "Input Format" section right after the sentence about
receiving "enriched prospect profiles and warm path data" that explicitly
documents the expected structure and any transformation rules between upstream
agents: enumerate fields produced by enrichment-agent (e.g., Person details,
Company intel, Recent Activity, Personalization Hooks) and by mutual-mapper
(e.g., Target name/handle, Via, Relationship, Suggested approach), and map how
those natural-language fields must be parsed or renamed to the
outreach-drafter's expected output fields (e.g., Referenced:, Warm path:,
Confidence:) so the agent knows to parse "Personalization Hooks" text and
convert mutual-mapper "Via/Relationship/Suggested approach" into the Warm path
entries.

In `@skills/lead-intelligence/SKILL.md`:
- Line 144: Replace the un-hyphenated phrase in the SKILL.md line "GitHub: open
source contributions (for developer-centric leads)" with the hyphenated compound
adjective form "open-source contributions" so it reads "GitHub: open-source
contributions (for developer-centric leads)"; locate the string "GitHub: open
source contributions (for developer-centric leads)" and update it accordingly.

In `@skills/remotion-video-creation/rules/assets/text-animations-typewriter.tsx`:
- Around line 20-32: Add fail-fast validation in getTypedText to guard against
invalid timing parameters: check that charFrames and pauseFrames are positive
integers and that pauseAfter is a valid index/range; if any check fails, throw a
clear Error (e.g., "getTypedText: charFrames must be > 0, got X"). Also add the
same validation for the cursor-blink routine that uses blinkFrames (the function
handling blinkFrames around lines 52-60): ensure blinkFrames > 0 and throw a
descriptive Error if not. Keep messages specific to the parameter and function
name so failures point to the exact invalid value and location.

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="skills/remotion-video-creation/rules/animations.md">

<violation number="1" location="skills/remotion-video-creation/rules/animations.md:12">
P3: The example code uses `useVideoConfig` and `interpolate` without importing them, so the snippet won’t compile as written. Include the missing imports so readers can copy/paste it successfully.</violation>
</file>

<file name="skills/remotion-video-creation/rules/videos.md">

<violation number="1" location="skills/remotion-video-creation/rules/videos.md:41">
P2: The trimming section says `trimBefore`/`trimAfter` are in seconds, but the example (and the audio guide) treats them as frame counts (`2 * fps`). This inconsistency will mislead readers about the expected units.</violation>
</file>

<file name="skills/remotion-video-creation/SKILL.md">

<violation number="1" location="skills/remotion-video-creation/SKILL.md:16">
P2: These rule links point to files that don’t exist in the repo, so readers will hit broken links. Add the referenced rule files or update the links to the correct locations.</violation>
</file>

<file name="skills/autonomous-agent-harness/SKILL.md">

<violation number="1" location="skills/autonomous-agent-harness/SKILL.md:11">
P3: Use the standard skill section name “When to Use” so this skill follows the documented format and stays consistent with other skills.</violation>
</file>

<file name="skills/remotion-video-creation/rules/trimming.md">

<violation number="1" location="skills/remotion-video-creation/rules/trimming.md:17">
P2: `useVideoConfig()` returns a config object; assigning it directly to `fps` makes the arithmetic in this example evaluate to `NaN`. Destructure `fps` from the config like the other Remotion examples.</violation>
</file>

<file name="skills/remotion-video-creation/rules/extract-frames.md">

<violation number="1" location="skills/remotion-video-creation/rules/extract-frames.md:91">
P2: Abort inside the sample loop only breaks and resolves successfully, so callers can’t detect cancellation (the try/catch example will log completion even when aborted). Throw on abort in the loop to match the earlier abort checks and the documented behavior.</violation>
</file>